home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
bbs
/
lndl27.zip
/
LNDL.CFG
< prev
next >
Wrap
Text File
|
1996-06-26
|
11KB
|
431 lines
; lndl.cfg for v2.6g
; Note: this file is 'correct' for Zone 1 -only-. For instance, the Z1
; nodelist says 'V32b' is proper while Z2 says 'V32B' is proper. You'll
; need to modify this file for you zone. 'Othernets' may add other flags
; and speeds as required.
; lines starting with ';' are comments and are ignored
; blank lines are ignored
; | Lines starting with '|' are new for this version.
; config lines must begin with a keyword
; valid keywords are:
; valid = valid modem flags
; suggest = suggested fixes for 'bad' flags
; exclusive = if the first flag is present then the second flag is redundant
; speed = valid modem speeds
; Valid and Speed keywords are required - there must be at least one of each.
; Suggest and Exclusive flags are -not- required. LNDL will run up to 30%
; faster without them.
; In non case sensitive mode, config flags and nodelist flags are converted
; to uppercase. Also, 'redundant' suggest and exclusive config flags are
; stripped. Thus, in case sensitive mode, the following lines are recognised:
;suggest V32B V32b
;suggest v32B V32b
;suggest v32b V32b
;suggest 32b V32b
;suggest 32B V32b
;suggest V32bis V32b
;suggest V32Bis V32b
;suggest V32BIS V32b
;exclusive V32B V32
;exclusive V32b V32
;exclusive V42B V42
;exclusive V42b V42
;exclusive HST MNP
;exclusive H14 MNP
; But in non case sensitive mode, these are 'reduced' to:
;suggest 32B V32B
;suggest V32BIS V32B
;exclusive V32B V32
;exclusive V42B V42
;exclusive HST MNP
;exclusive H14 MNP
; Valid flags may include wildcards. This is to allow for 'Txy' flags and
; HUB: flags that some nets use. Example:
; T??
; HUB:*
; =====================================================================
; valid flags, accurate for Z1 as of 11/2/95
valid CM
valid MO
valid LO
valid V21
valid V22
valid V29
valid V32
valid V32b
valid V33
valid V34
valid V42
valid V42b
valid MNP
valid H96
valid HST
valid H14
valid H16
valid MAX
valid PEP
valid CSP
valid ZYX
valid VFC
valid V32T
valid MN
valid XA
valid XB
valid XC
valid XP
valid XR
valid XW
valid XX
valid QMM
valid Guucp
valid T??
; suggested 'fixes'
suggest cm CM
suggest mo MO
suggest Mo MO
suggest lo LO
suggest Lo LO
suggest v21 V21
suggest v22 V22
suggest v29 V29
suggest v32 V32
suggest V32B V32b
suggest v32B V32b
suggest v32b V32b
suggest 32b V32b
suggest 32B V32b
suggest V32bis V32b
suggest V32Bis V32b
suggest V32BIS V32b
suggest v33 V33
suggest v34 V34
suggest V.34 V34
suggest v42 V42
suggest V42B V42b
suggest v42B V42b
suggest v42b V42b
suggest 42b V42b
suggest 42B V42b
suggest V42bis V42b
suggest V42Bis V42b
suggest V42BIS V42b
suggest mnp MNP
suggest h96 H96
suggest hst HST
suggest h14 H14
suggest h16 H16
suggest max MAX
suggest pep PEP
suggest csp CSP
suggest zyx ZYX
suggest Zyx ZYX
suggest ZyX ZYX
suggest ZXY ZYX
suggest vfc VFC
suggest VfC VFC
suggest Vfc VFC
suggest vFC VFC
suggest UVFC VFC
suggest V.FC VFC
suggest VCF VFC
suggest UV32T V32T
suggest v32T V32T
suggest V32t V32T
suggest v32t V32T
suggest V32ter V32T
suggest V32Terbo V32T
suggest V32TERBO V32T
suggest mn MN
suggest xa XA
suggest xb XB
suggest xc XC
suggest xp XP
suggest xr XR
suggest xw XW
suggest xx XX
suggest qmm QMM
suggest guucp Guucp
suggest GUUCP Guucp
suggest GUucp Guucp
suggest UUCP Guucp
suggest ISDNA UISDNA
suggest ISDNB UISDNB
suggest ISDNC UISDNC
suggest ISDN UISDN[A/B/C]
; valid user flags
suggest NEC UNEC
suggest REC UREC
suggest ZEC UZEC
suggest Z19 UZ19
; exclusive flags
; | NOTE: Due to discussion in local and regional sysop echoes I have
; | commented out soem of the default exclusive flags mentioned in the
; | following text.
; -IF- the first flag is present -THEN- the second flag is redundant.
; The following flags are listed as redundant according to a conversation I had
; with Craig Ford in the COMM echo.
; There are two points to notice:
; First, V42b does -not- 'necessarily' imply V42, but is listed as such because
; it works for everyone.
; Second, a very large number of nodes are listed with redundant V32T/V32b and
; V34/V32b flags, at odds with the published spec.
; -IF- you don't care to see all these V32T/V34/V32b errors, just comment them
; out of the exclusives config.
; Date: Sun Dec 17 1995 14:44:58
; From: Craig Ford
; To: jim barchuk
; Subj: modem capability
; Area: comm
;
; jim barchuk wrote the following to all, and I quote (in part):
;
; jb> My question is can someone post a -full- list of implied modem
; jb> capabilities. I'm simply unfamiliar with the newer protocols.
;
; ITU-T Modulation Protocols:
;
; V.21 implies no other support
; V.22 imples V.21 support
; V.22bis implies V.22 support
; V.29 implies no other support
; V.32 implies V.22bis support
; V.32bis implies V.32 support
; V.34 implies V.32bis support
;
; Proprietary Modulation Protocols:
;
; Bell 103 implies no other support
; Bell 212A implies Bell 103 support
; CSP implies V.22bis support
; - also implies support for MNP error control
; H96 implies V.22bis support
; - also implies support for LAP-B error control
; HST implies V.22bis support
; - also implies support for MNP error control
; H14 implies HST support
; H16 implies HST and H14 support
; MAX implies V.22bis support
; - also implies support for MNP error control
; PEP implies V.22bis support
; - also implies support for MNP error control
; V.FC implies V.32bis support
; V.32T implies V.32bis support
; ZYX imples V.32bis support
;
; ITU-T error control protocols:
;
; V.42 implies MNP support (service levels 2-4)
;
; Proprietary error control protocols:
;
; HST imples MNP support
; MNP implies support for service levels 2-4
;
; ITU-T data compression protocols:
;
; V.42bis implies no other support
;
; Proprietary data compression protocols:
;
; MNP implies support down to service level 5
;
; jb> Why does this leave me confused:
;
; > NOTE: Each V.nnbis complements, but is separate from, its V.nn
; > counterpart. Theo Irmer, director of the ITU-TSS wrote: "I would
; > like you to note further, that the use of "bis", "ter" etc. in the
; > numbering of Recommendations (e.g. V.42bis) does not necesarily
; > mean a simple expansion of the Recommendation having the original
; > number, (e.g. V.42). In other words, V.42 and V.42bis should be
; > considered as independent, separate Recommendations."
;
; Perhaps because that is actually the way it is as opposed to the "wisdom" you
; may see expressed herein.
;
; jb> This seems to say the V42b does -not- imply V42, at odds with what
; jb> I hear elsewhere.
;
; Precisely the point of my missive above. V.42bis doesn't absolutely imply
; V.42, as V.42bis can be implemented over _any_ suitable error control layer.
;
; The general reality of what vendors have implemented is what I have listed in
; the "implication" chart above, but it should not be taken as an absolute.
;
; Regards....
;
; Craig
;
; aka: cford@ix.netcom.com
;
; -!- timEd/2 1.10+
; ! Origin: Dayze of Futures Past * V.Everything * 713-458-0237 * (1:106/2001)
;
;
; Date: Thu Dec 21 1995 06:48:08
; From: Craig Ford
; To: jim barchuk
; Subj: modem capability
; Area: comm
;
; jim barchuk wrote the following to Craig Ford, and I qu